Fix typo in track-merge-target and track-merge-message #4041
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
arturcic
approved these changes
May 24, 2024
|
Thank you @DSpirit for your contribution! |
|
🎉 This issue has been resolved in version 6.0.0-rc.2 🎉 Your GitReleaseManager bot 📦🚀 |
This was referenced Jul 25, 2025
This was referenced Aug 5, 2025
This was referenced Aug 22, 2025
This was referenced Sep 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix typo in track-merge-target and track-merge-message
Description
Due to the default configuration of the GitHubFlow/v1 having a typo, the GitVersion task fails with an unkown property.
Could not build the configuration instance because following exception occurred: 'Property 'tracks-merge-target' not found on type 'GitVersion.Configuration.BranchConfiguration'.' Please ensure that the /overrideconfig parameters are correct and the configuration file is in the correct format.Related Issue
https://github.com/GitTools/GitVersion/releases/tag/6.0.0-rc.1
Motivation and Context
Fix the GitVersion task for GitHubFlow/v1.
How Has This Been Tested?
Screenshots (if appropriate):
Checklist: